-
-
Notifications
You must be signed in to change notification settings - Fork 844
Removed Muyin Zheng from Home Unite Us page #8127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removed Muyin Zheng from Home Unite Us page #8127
Conversation
|
Want to review this pull request? Take a look at this documentation for a step by step guide! From your project repository, check out a new branch and test the changes. |
t-will-gillis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @michael-4 - Thanks for resubmitting this PR. The branches are good, there are before and after screenshots, and the code change is clean now. Looks good- just have a couple requests.
- Please change the "Fixes: " reference to be the original issue instead of the previous PR
- For "Why did you make the changes...", the answer that you had on the previous PR is what you want here, i.e. "To keep the list of members up to date"- this is the reason for the issue.
- For the "CodeQL Alerts", you do not have any so please check "I have checked this PR for CodeQL alerts and none were found."
Almost there- thanks for working on this
|
Hi @t-will-gillis thanks again for your continued feedback! I've made the changes you said, hopefully it's all good now |
andyvu923
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @michael-4 , the PR looks good to me! The code changes are clean and relevant, the before and after pictures are provided and correct, and all the information in the PR seems correct as well. PR Approved 👍👍
t-will-gillis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @michael-4 - thank you for making the edits, and thank you for working on this issue. Everything looks great.
Fixes #7483
What changes did you make?
Why did you make the changes (we will use this info to test)?
CodeQL Alerts
After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.
Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown
Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.
Instructions for resolving CodeQL alerts
If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.
In general, CodeQL alerts should be resolved prior to PR reviews and merging
Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)
Visuals before changes are applied
![image]

Visuals after changes are applied
![image]
